Release 10.1A: OpenEdge Application Server:
Administration

AppServer startup and shutdown

You typically configure AppServer instances and NameServers to start up at system startup time. The Progress Explorer framework provides a graphical user interface and an equivalent set of command-line utilities that you can use to configure, start up, and manage NameServers and AppServer instances. For more information, see the "AppServer administration framework" section.

SSL-enabled AppServer startup requirements

An SSL-enabled AppServer instance cannot start if the correct key password is not provided, the server key store entry cannot be found, or the server digital certificate is out of date. See the "SSL-enabled AppServer operation" section for more information.

OpenEdge startup parameters

You can also configure the AppServer agent to pass a set of OpenEdge startup parameters to any AppServer agents that it starts. These startup parameters have the same effect on each AppServer agent as the startup parameters used to start a Progress 4GL client. For example, one of the startup parameters you specify might be the Database (-db) parameter to indicate that all AppServer agents in the pool are to connect to a specific database when they start up.

AppServer registration

When you start an AppServer instance configured to use a NameServer, the first thing the AppServer agent does is to register with the controlling NameServer that you specified during AppServer configuration. When you shut down an AppServer instance, the AppServer agent immediately unregisters the AppServer with the controlling NameServer, ensuring that the NameServer no longer makes this AppServer available for client connection requests.